…#895)

## Summary
Bump `entity-recognition-with-llms` to Ray 2.56.0.

## Changes
- `BUILD.yaml` `cluster_env.image_uri`:
`anyscale/ray-llm:2.55.1-py311-cu128` →
`anyscale/ray-llm:2.56.0-py312-cu130`.
- `templates/entity-recognition-with-llms/containerfile` `FROM`: same
bump.
- **Forced py311→py312 + cu128→cu130 jump.** `anyscale/ray-llm:2.56.0`
on Docker Hub only publishes `py312-cu130` (no `py311-cu128` variant);
this matches the forced-variant handling used for every other
`ray-llm`-based template on this Ray version (see #884, #887, #889,
#892). Tag verified on Docker Hub.
- No `python_depset.lock` for this template (no entry in
`dependencies/template.depsets.yaml`), so the image bump is the whole
change.

## Tests / validation
- **Local:** `pre-commit run --all-files` — passed. `python
ci/validate_build_yaml.py` — passed.
- **CI:** Buildkite `template-test` build
[#506](https://buildkite.com/anyscale/template-test/builds/506) —
**passed** on commit `dee61081` (~44 min end-to-end; a first attempt was
auto-cancelled at ~13 min into training due to a Buildkite agent
shutdown, and the retry ran the full ~34 min LoRA SFT training cleanly
on the new py312-cu130 base).

## Publish
- `BUILDKITE_API_TOKEN` on this Cursor Cloud agent lacks the
`write_builds` scope required to trigger `tmpl-publish` via API
(`create_build` returns `Your access token doesn't have the write_builds
scope`). **Please trigger the publish manually** after merge —
[tmpl-publish pipeline](https://buildkite.com/anyscale/tmpl-publish),
branch `master`, message `entity-recognition-with-llms`; then unblock
`input-tmpl-name` with `tmpl-name=entity-recognition-with-llms`,
`tmpl-branch=main`, `tmpl-commit=HEAD` per `publish-to-backend.md`.

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Aydin Abiar <Aydin-ab@users.noreply.github.com>

## Summary
Bump `e2e-rag-deepdive` to Ray 2.56.0.

The Anyscale `ray-llm` image only ships as `py312-cu130` for Ray 2.56.0
(per `dependencies/depsets/rayllm_2.56.0_py312_cu130.lock`), so this
bump also migrates the template's base-image Python (3.11 → 3.12) and
CUDA (12.8 → 13.0) variants alongside the Ray version. Same "forced
py311→py312 + cu128→cu130 jump on the LLM image" path other 2.56.0
`ray-llm` bumps have taken (e.g. #892, #891, #887).

## Changes
- `templates/e2e-rag-deepdive/containerfile`: `FROM
anyscale/ray-llm:2.55.1-py311-cu128` → `2.56.0-py312-cu130` (tag
verified on Docker Hub).
- Rebuilt and pushed the template's custom image:
`us-docker.pkg.dev/anyscale-workspace-templates/workspace-templates/e2e-rag-deepdive:2.56.0`.
- `BUILD.yaml`: `cluster_env.byod.docker_image` and `ray_version` →
`2.56.0`.

No `python_depset.lock` / `template.depsets.yaml` entry for this
template (BYOD-only), so no dependency-lock recompile needed.

## Fix iterations
None — CI passed on the first `/test-template` dispatch.

## Tests / validation
- **Local:** `python3 ci/validate_build_yaml.py --no-network` — passed
(56 entries). `pre-commit run --all-files` — passed.
- **CI:** Buildkite `template-test` build
**[#508](https://buildkite.com/anyscale/template-test/builds/508)** —
**passed** (all 3 jobs green; end-to-end ~45 min, well under the
template's 7200s test budget).

## Publish
The read-only Buildkite token in this Cursor Cloud environment lacks the
`write_builds` scope, so this automation cannot trigger the
`tmpl-publish` build itself (a known limitation across all
`template-updater` runs — see prior PRs). After merging, please trigger
the publish manually per
`.claude/skills/template/references/publish-to-backend.md`:

- Pipeline: <https://buildkite.com/anyscale/tmpl-publish>
- Trigger a new build on `master`.
- On the `input-tmpl-name` gate, enter:
  - `tmpl-name=e2e-rag-deepdive`
  - `tmpl-branch=main`
  - `tmpl-commit=HEAD`
- Wait for `build-template` + `test-template` green, then unblock
`block-publish-dev` → `block-publish-staging` →
`block-publish-production` in sequence.

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Aydin Abiar <Aydin-ab@users.noreply.github.com>